Next: 3.2 Functions
Up: 3 Functions and Errors
Previous: 3 Functions and Errors
Where possible, as in X, when a request terminates with an error, the request
has no side effects.
The error codes that may be generated by a request are described with
that request.
The following table summarizes the GLX-specific error codes that are
visible to applications:
- GLXBadContext
A value for a Context argument does not name a Context.
- GLXBadContextState
An attempt was made to switch to another rendering context while
the current context was in RenderMode GL _FEEDBACK or
GL _SELECT, or a call to glXMakeCurrent was made
between a glBegin and the corresponding call to glEnd.
- GLXBadCurrentWindow
The current Drawable of the calling thread is a window that is no
longer valid.
- GLXBadDrawable
The Drawable argument does not name a Drawable
configured for OpenGL rendering.
- GLXBadPixmap
The Pixmap argument does not name a Pixmap that is
appropriate for OpenGL rendering.
The following error codes may be generated by a faulty
GLX implementation, but would not normally be visible to clients:
- GLXBadContextTag
A rendering request contains an invalid context tag.
(Context tags are used to identify contexts in the protocol.)
- GLXBadRenderRequest
A glXRender request is ill-formed.
- GLXBadLargeRequest
A glXRenderLarge request is ill-formed.
- GLXUnsupportedPrivateRequest
May be returned in response to either a glXVendorPrivate request
or a glXVendorPrivateWithReply request.
Mark Segal
Wed Jan 11 18:38:15 PST 1995